Release 10.1A: OpenEdge Getting Started:
Database Essentials

Fast CPUs versus many CPUs

In a best-case scenario, you would have a large number of fast CPUs in your system. However, in many cases you can only afford one or the other: multiple, slower CPUs, or a single, faster CPU. The benefit of fast CPUs is that they run single-threaded operations very quickly. An example of a single-threaded operation could be end-of-day processing; you might need to apply all of your payments prior to being able to run your general ledger trial balance. On the other hand, multiple CPUs allow you to do two different operations simultaneously. One user can be entering orders while the other is shipping products. This has obvious benefits to the business in terms of efficiency.

So, how do you decide? The best way to decide is to look at your options and your application to determine the best solution. For example, an application that does a significant amount of single-threaded operations will benefit from a design that has fast CPUs, even at the expense of having fewer total CPUs in the system. An application that is mostly data entry will benefit from a design that has more CPUs, even at the expense of each CPU being slower. This is another case where having a deep understanding of your application and workload will allow you to make intelligent decisions in the system area.